Resolution failed for 1 modules:
--------------------------------------------
  io.get-coursier:coursier-cli_2.12:2.1.15 
	not found: /root/.ivy2/local/io.get-coursier/coursier-cli_2.12/2.1.15/ivys/ivy.xml
	not found: https://repo1.maven.org/maven2/io/get-coursier/coursier-cli_2.12/2.1.15/coursier-cli_2.12-2.1.15.pom

🤔

https://repo1.maven.org/maven2/io/get-coursier/coursier-cli_2.12/2.1.15/coursier-cli_2.12-2.1.15.pom

I think it's no longer published for 2.12, why do we actually need it?

Ach, we publish only using 2.12, do we actually need to continue publishing the image? Should we not move it to coursier?

I guess we have two options:

• switch to 2.13 here
• add M1 publish to coursier

@alexarchambault is it time to move arm publishing to coursier?

@tgodzik we could move it to coursier if we gave up on the Linux arm64 launchers. We need the custom runner for that. As for the MacOS aarch64, that could already be moved, I suppose.
We track it here:

• Switch building Linux arm64 launchers to a GitHub-hosted runner scala-cli#3051

Sounds like we need to switch to 2.13 here. 🤔

We can remove the macos jobs though next coursier/coursier#3148

java.lang.UnsupportedClassVersionError: coursier/bootstrap/launcher/Launcher has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file versions up to 55.0

We need to switch to JDK 17 (or wait for next release, though it's native image so it's not necessary to publish on JDK 8)